Handle consistency related error that occurs possibly due to app ID collision in another tenant #109
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…ollision in another tenant This occurs when the backing application for the service principal has not fully replicated. We'd usually see an ErrorServicePrincipalInvalidAppId here but sometimes this new error occurs within a 403 response.
manicminer
added
api-bug
manicminer
requested review from
koikonom,
tombuildsstuff,
katbyte and
jackofallops
manicminer
deleted the
service-principal-error-consistency-with-app-id-collision
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This occurs when the backing application for the service principal has not fully replicated. We'd usually see an
ErrorServicePrincipalInvalidAppIdhere but sometimes this new error occurs within a 403 response.Related: hashicorp/terraform-provider-azuread#581